Coming from a Latin American the idea of re-starting your life across the country for college and then again for work (multiple times sometimes) while away from family and friends is very foreign.
A lot of the conversation around modern American youth feeling isolated, lacking socialization and not building strong relationships seems that stem from this drive.
Another thing that’s really weird and related is another recurring theme in the American ethos: the cultural shame that comes with living “at home” or staying in the same small town for your whole life. Somehow they made it so living close to your family and friends for your 20s-30s and maybe forever means you’re a “loser”.
I don't understand why they are spending so much time and effort trying to put a positive spin on this whole for-profit thing. No one is buying it. We all know what's going on. Just say "we want to make lots of money" and move on with your lives.
Our current structure does not allow the Board to directly consider the interests of those who would finance the mission and does not enable the non-profit to easily do more than control the for-profit.
I kind of thought that was the point of the current structure.
<3 This has been a work of passion for the past two years of my life (off and on). I hope anyone who uses this can feel the love and care I put into this, and subsequently the amazing private beta community (all ~5,000 strong!) that helped improve and polish this into a better release than I ever could alone.
Ghostty got a lot of hype (I cover this in my reflection below), but I want to make sure I call out that there is a good group of EXCELLENT terminals out there, and I'm not claiming Ghostty is strictly better than any of them. Ghostty has different design goals and tradeoffs and if it's right for you great, but if not, you have so many good choices.
Shout out to Kitty, WezTerm, Foot in particular. iTerm2 gets some hate for being relatively slow but nothing comes close to touching it in terms of feature count. Rio is a super cool newer terminal, too. The world of terminals is great.
I’ve posted a personal reflection here, which has a bit more history on why I started this, what’s next, and some of the takeaways from the past two years. https://mitchellh.com/writing/ghostty-1-0-reflection
I've been thinking about the notion of "reasoning locally" recently. Enabling local reasoning is the only way to scale software development past some number of lines or complexity. When reasoning locally, one only needs to understand a small subset, hundreds of lines, to safely make changes in programs comprising millions.
I find types helps massively with this. A function with well-constrained inputs and outputs is easy to reason about. One does not have to look at other code to do it. However, programs that leverage types effectively are sometimes construed as having high cognitive load, when it in fact they have low load. For example a type like `Option>` carries a lot of information(has low load): we might not have a set of user ids, but if we do they are unique.
The discourse around small functions and the clean code guidelines is fascinating. The complaint is usually, as in this post, that having to go read all the small functions adds cognitive load and makes reading the code harder. Proponents of small functions argue that you don't have to read more than the signature and name of a function to understand what it does; it's obvious what a function called last that takes a list and returns an optional value does. If someone feels compelled to read every function either the functions are poor abstractions or the reader has trust issues, which may be warranted. Of course, all abstractions are leaky, but perhaps some initial trust in `last` is warranted.
Christmas of 1981 in Athens, Greece. I was 15. Father had died 3 years ago from heart attack at 42. His last words to my mother: "Educate the kids".
She did her best, given that my grandfather was old fashioned and had stopped her from going to school after she became twelve, although she was among the smartest in her class.
That Christmas she had bought me the brand new then Sinclair ZX81 personal computer. We were visiting the grandparents in a small village near Athens.
I spend the night by the fireplace with a small portable TV and the machine, typing in games published in the UK PC magazines of that time and occasionally watching the Chrstmas shows. Debugging my typos was the way I learned how programming works.
Nothing really interesting here, but I am remembering that night again and again so when I saw the prompt I felt I should share. Merry Christmas everyone.
I'm Jewish, so all my Christmas's growing up were kinda the same. Sleep in, have brunch, wander over to my neighbor's house around noon to see what kind of loot they got and help them play with their new toys. Sometimes we'd go out for Chinese food and a movie.
But my favorite was Christmas 1999. My girlfriend was out of town with her family and there was no reason to go home to mine, so I was alone (my roommates were with their families too). I decided to go to the movies in Emeryville.
I was going to see Galaxy Quest, Bicentennial Man, and Man on the Moon. The timing lined up perfectly to see all three. About 50 other people were there to do the same thing. When it was time to go in for the first movie, a staff member came out and told us that it would start about 30 minutes late. This would of course cause us to miss all the other movies.
About 30 people stepped forward at the same time and asked to speak to the manager. :). We explained to him that it would throw our whole schedule off. Since it was Christmas, he was kind enough to adjust the schedule so that we could all see all three movies.
That was a great day.
I don't know why, but I imagine a situation where all communication has broken down, and the only working sensor is the one in the piss-tank, and the astronauts have to communicate in morse by modulating the delta in the tank. And some guy with ADHD, and this menu bar app installed, is going to figure out whats going on what is going on, and save them all. (Hey, Hollywood - if this turns into a movie - I want my royalties)
Absolutely! Realtime data will require a subscription, which will also include an LLM analysis of the past week's data. I think one of the VCs funding my upcoming disruptive space station piss tank telemetry platform requested that.
I'm pretty sure I can also shove a blockchain in there somewhere too even though they're a bit passé.
> I found out about the data stream from https://iss-mimic.github.io/Mimic/, which has considerably more and more interesting stats than just how full the piss tank is.
> I will not be adding any of them.
This, right here, is how you communicate non-goals of a project. Just perfect open-source communication best practices. We all stand to learn from this project.
(Though, predictably, some of us sit to interact with it.)
I've made more friends more easily in my 40s than any other time in my life, and I'm a relatively quiet and disagreeable person.
Making connections with people you're around frequently is easy. The problem is that adult life doesn't throw you into those situations post-college outside of work.
Now it's on you. Find a group. Sports are the easiest. You will absolutely make strong, long lasting friendships if you play sports. It doesn't matter if you're athletic or talented.
You just gotta show up and see the same people every week over and over. If you're a reasonably well adjusted person (and even that sometimes doesn't matter) you will make friends.
Again, making connections and friends is easy. Being around the same people regularly is difficult. Solve that problem and the friendships will come with little effort.
I have found that people generally understand the value of friendship and are welcoming to newcomers. It's been a very refreshing surprise as I've gotten older.
Get out there!
- No serious hedge funds or other activists involved in this, ie no adults involved, check
- Fully audited financials not being questioned, check
- CEO and CFO constantly acknowledging the Foundary unit wasn't profitable in quarterly updates, check.
The former CEO was brought in to to try and keep Intel a fully integrated business that designed and manufactured chips. He was very clear upfront about his plan to not divest the foundry and instead to try and build it back up.
It didn't' work, that's not a crime. He left because his plan didn't work. That's what happens to CEO's who try and fail to implement a business plan.
This is just an ambulance chaser lawsuit that doesn't look like it will go anywhere at all.
If there was any merit at all then the board would also be involved in going after the former CEO and CFO.
This question reminds me of the first time I met a blind programmer.
I asked him how he managed to code, and he replied with something that stayed with me: a good programmer should organize software in such a way that every piece of code has a clear and logical place. The organization should be so intuitive that anyone could build a mental model of the structure and navigate it easily, even without seeing it.
It felt like something out of a Yoda or Mr. Miyagi lesson. Skeptical, I asked his colleagues if he was truly able to code or if he was just exaggerating. To my surprise, they told me not only was he capable, but he was the best programmer they had ever worked with. They said no one else came close to writing code as organized as his.
That conversation changed my perspective. Ever since, whenever I’m unsure where to place new code, I don’t think about DDD or any specific methodology. Instead, I try to follow the logic and structure of the project in a way that feels natural and easy to follow later.
Later in life, I met two other blind programmers and heard similar stories about their ability to produce well-organized code.
To bring this back to the original question: I view LSP/IDE features the same way those programmers view "visual aids." Code should be organized according to a clear and logical structure that makes it easy to navigate.
Relying on features like Ctrl+Click to find where things are located worries me. Why? Because it can mask structural flaws in the codebase. If we can't intuitively figure out where something belongs, that’s a sign the codebase lacks structure—and that should motivate us to refactor it.
Not only do I avoid using LSP features, but I’m also opposed to their use. While they can help with navigation, they may prevent developers from experiencing and addressing the underlying structural issues in their code.
I’d rather have the pdf than a custom tool. Especially considering the tool will be unique to the practice or emr. And likely expensive to maintain.
PDFs suck in many ways but are durable and portable. If I work with two oncologists, I use the same pdf.
The author means well but his solution will likely be worse because only he will understand it. And there’s a million edge cases.
I'm sure the debate over the definition of AGI is important and will continue for a while, but... I can't care about it anymore.
Between Perplexity searching and summarizing, Claude explaining, and qwen (and other tools) coding, I'm already as happy as can be with whatever you want to call this level of intelligence.
Just today I used a completely local AI research tool, based on Ollama. It worked great.
Maybe it won't get much better? Or maybe it'll take decades instead of years? Ok. I remember not having these tools. I never want to go back.
Note that the measurements in the paper were made before they fixed a bug where they confused bits and bytes. So SQLite only used 1/8 of the reserved bloom filter space, thus increasing the false positive rate significantly:
https://sqlite.org/src/info/56d9bb7aa63043f5
I found and reported the bug because I wanted to know how the bloom filters work in SQLite for my uni seminar paper. Still wondering if one can find those kind of bugs with test cases.
The original answer to "why does FastMail use their own hardware" is that when I started the company in 1999 there weren't many options. I actually originally used a single bare metal server at Rackspace, which at that time was a small scrappy startup. IIRC it cost $70/month. There weren't really practical VPS or SaaS alternatives back then for what I needed.
Rob (the author of the linked article) joined a few months later, and when we got too big for our Rackspace server, we looked at the cost of buying something and doing colo instead. The biggest challenge was trying to convince a vendor to let me use my Australian credit card but ship the server to a US address (we decided to use NYI for colo, based in NY). It turned out that IBM were able to do that, so they got our business. Both IBM and NYI were great for handling remote hands and hardware issues, which obviously we couldn't do from Australia.
A little bit later Bron joined us, and he automated absolutely everything, so that we were able to just have NYI plug in a new machine and it would set itself up from scratch. This all just used regular Linux capabilities and simple open source tools, plus of course a whole lot of Perl.
As the fortunes of AWS et al rose and rose and rose, I kept looking at their pricing at features and kept wondering what I was missing. They seemed orders of magnitude more expensive for something that was more complex to manage and would have locked us into a specific vendor's tooling. But everyone seemed to be flocking to them.
To this day I still use bare metal servers for pretty much everything, and still love having the ability to use simple universally-applicable tools like plain Linux, Bash, Perl, Python, and SSH, to handle everything cheaply and reliably.
I've been doing some planning over the last couple of years on teaching a course on how to do all this, although I was worried that folks are too locked in to SaaS stuff -- but perhaps things are changing and there might be interest in that after all?...
I was the only person working on it for ~2 years, and I wrote the majority of the code in the first version that shipped. That said, I’m definitely glad that I eventually found someone else (and later a whole team) to work on it with me, and it wouldn’t have been as successful without that.
When people think of a binary translator, they usually just think of the ISA aspects, as opposed to the complicated interactions with the OS etc. that can consume just as much (or even more) engineering effort overall.
This is me! Didn’t expect to see this on here, but I’m looking forward to working with everyone else at the Lean FRO and the wider Lean community to help make Lean even better.
My background is in mathematics and I’ve had an interest in interactive theorem provers since before I was ever a professional software engineer, so it’s a bit of a dream come true to be able to pursue this full-time.